Content recordation techniques

ABSTRACT

Content recordation techniques are described. In an implementation, a method includes querying electronic program guide (EPG) data to determine if a content item described in a recording document is available for recording. If the content item is available, a reference is added to a recording list for causing recordation of the content item.

TECHNICAL FIELD

The present invention generally relates to the field of content and in particular to content recordation techniques.

BACKGROUND

Users are continually exposed to an ever increasing variety of clients that provide network access, such a set-top boxes, wireless phones, computers, and so on. A user of a set-top box, for instance, may view traditional television programming obtained from a broadcast network for display on a television, as well as order pay-per-view movies, receive video-on-demand (VOD), play “live” video games, and so on. Likewise, a user of a wireless phone may place and receive traditional telephone calls, as well as read email, download digital music, and so on.

Another such example is a digital video recorder (DVR). A DVR typically includes non-volatile storage (e.g., a hard disk) that enables the user to record desired content. DVR's also offer control functionality, such as the ability to pause content that is currently being broadcast and allows viewers to watch the content, while still in progress, from the point it was paused. The DVR plays back the content from storage, starting at the pause event, while continuing to record the currently-broadcast content. Additionally, the DVR may support other control functions, such as rewinding, fast forwarding a stored program, slow motion playback, and the like.

To record content using a DVR, a user was typically required to directly interact with the DVR itself. In some instances, the user could configure the DVR to record related content by specifying parameters to be matched with those of available content to locate potentially desirable content. For example, the user could specify the title of a television program so that the DVR would record each television program having that title. However, the user was not assured that the DVR would record a particular content item of interest. In other words, the user could not be certain that the potentially desirable content recorded by the DVR corresponded with the actual content the user wished to record. For example, although the DVR may be configured to record a particular television program, the DVR might fail to record a special regarding the actors in that particular television program. Therefore, when the user was located “away” from the DVR, the user could not cause the DVR to record the particular content item, even if the user had access to one or more of the clients that provide network access as previously described.

Accordingly, there is a continuing need for improved content recordation techniques.

SUMMARY

Content recordation techniques are described. The content recordation techniques may be utilized when the user is local to and remote from the client. For example, a user, when remotely located from a client configured as a digital video recorder (DVR), interacts with a remote device that is configured as a wireless phone. The user utilizes the wireless phone to access a review of a television program via the Internet. Based on the review, the user invokes a recording document that is embedded in the review to be communicated to the remote client. The recording document describes the television program, such as by describing a title, actors, broadcast time, service (e.g., channel) that broadcasts the television program, and so on.

Upon receipt of the recording document, the remote client executes a parser module to examine the recording document to determine if the television program described in the recording document is available for being recorded by the remote client. For instance, the recording document may be compared with electronic program guide (EPG) data that is received from a head end, EPG data service, and so on. The EPG data may be utilized to determine if the television program is available. The EPG data may also be utilized to determine how the television program is to be recorded, such as by supplying a channel and broadcast start time. If the television program is available, a reference to the television program is added to a recording list based on the EPG data. For example, the broadcast channel and the broadcast start time may be added to the recording list. The recording list is then utilized by the remote client to cause the client to record the content. In another instance, the recording document may cause the head end to cause the client to record the content, such as by examining EPG data stored at the head end to determine if the content is available for recording. If so, the head end causes the client the record the content. In a further instance, the recording document may cause the head end itself to record the content, such as in a network digital video recorder (NDVR) scenario.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of an environment in an exemplary implementation that includes a content provider that is communicatively coupled to a client over a network.

FIG. 2A is an illustration of an exemplary implementation showing a distribution server, the client, a head end, and a remote device of FIG. 1 in greater detail such that the head end is configured to record content.

FIG. 2B is an illustration of another exemplary implementation showing a distribution server, the client, a head end, and a remote device of FIG. 1 in greater detail such that the client is configured to record content.

FIG. 3 is an illustration of a system showing a variety of content recordation techniques as implemented by the distribution server and the client of FIG. 2A.

FIG. 4 is a flow diagram depicting a procedure in an exemplary implementation in which a recording document is utilized to record a particular content item.

FIG. 5 is an illustration of a system in an exemplary implementation in which a graphical user interface (GUI) is provided by a recording module to dynamically generate a recording document based on user input.

FIG. 6 is an illustration of a system in an exemplary implementation in which the recording module is executed to examine a textual description of content to dynamically generate a recording document.

FIG. 7 is a flow diagram depicting a procedure in an exemplary implementation in which a client dynamically generates a recording document that is utilized to determine availability of a particular content item for recording by the client.

The same reference numbers are utilized in instances in the discussion to reference like structures and components.

DETAILED DESCRIPTION

Overview

Content recordation techniques are described. In an implementation, a content recordation technique is described in which a client, such as a digital video recorder (DVR), is configured to record content streamed from a head end through use of a recording document that describes the content. The recording document may be provided in a variety of ways, such as embedded in a web site, shared via email or text messaging, submitted via an application programming interface (API), manually written by a user, and so on. The recording document is processed via a parser module to locate the content item that is described by the recording document. In one scenario, the parser module compares the recording document with an electronic program guide (EPG) that is stored on the client to find a matching content item that is described in the EPG data. If a sufficient match is found, a reference to the matching content item is added to a recording list based on the EPG data, such as a broadcast channel and time to record the matching content item. In another scenario, the head end processes the recording document provided by a remote device to determine whether the described content item is available. If so, the head end then causes the client to record the particular content item, such as through communication of a recording list to the client. Thus, a user may cause a particular content item to be recorded without direct interaction with the client.

In a further implementation, the head end stores client state data to process content recordation requests. For example, the head end may include client state data, such as ratings limits, favorite channels, levels of service, and so on, that is accessible locally by the head end. The head end may utilize this client state data to determine if the client is permitted to access the content item described by the recording document. If so, the head end may then cause the client to record the content. By performing the determination utilizing client state data at the head end, the head end provides an authoritative source for processing requests to record content by the client. This may result in a variety of increased functionality that is available to the user, such as an ability to change from an old client to a new client without manually updating client state data from the old client to the new client, remote initiation of content recordation without obtaining a connection with the client itself, and so on.

Exemplary Environment

FIG. 1 is an illustration of an environment 100 in an exemplary implementation showing a content provider 102 that is communicatively coupled to a client 104 over a network 106. The network 106 in the following implementations is an example of a wide area network (WAN), such as the Internet, and may also include a variety of other networks, such as a broadcast network, an intranet, a wired or wireless network, and so forth.

The client 104 is configured to receive content communicated from the content provider 102 over the network 106. The content provider 102 includes content 108(k), where “k” can be any integer from 1 to “K”, that is locally stored on the content provider 102. The content 108(k) may include a variety of data, such as television programming, video-on-demand, one or more results of remote application processing, and so on. The content provider 102 communicates the content 108(k) over a network 110 to a head end 112. The network 110 may be the same as or different from network 106. For example, the network 110 may represent a dedicated network connection between the content provider 102 and the head end 112 while network 106 is implemented by the Internet, both networks 106, 110 may be the Internet, and so on.

The content 108(k) may then be stored in a database 114 as content 116(n), where “n” can be any integer from 1 to “N”, on the head end 112 for communication over the network 106 to the client 104. In other words, the content 116(n) stored in the database 114 may be copies of the content 108(k) received from the content provider 102 over the network 110.

The head end 112, as illustrated, includes a distribution server 118 to format and distribute the content 116(n) over the network 106. Distribution from the head end 112 to the client 104 may be accomplished in a number of ways, including cable, RF, microwave, and satellite. Although the head end 112 is illustrated as separate from the content provider 102, the content provider 102 may also include the head end 112.

The head end 112 may also include a database 120 having a plurality of EPG data 122(m), where “m” can be any integer from one to “M”. The EPG data 122(m) is used to construct an EPG 124 for display by the client 104 to a user. The EPG 124, for instance, may enable the user to observe a listing of television programs that are currently being broadcast from the head end 112, as well as a listing of television programs that will be broadcast in the future. Additionally, the EPG 124 may allow the viewer to navigate to a television program (e.g., content 116(n)) from the EPG 124 itself. To provide additional information to the user, the EPG 124 may include one or more content characteristics that describe content represented in the EPG 124. The content characteristics may include title, broadcast time, broadcast channel, output duration of the content, plot description, a rating (e.g., G, PG, PG-13, R, etc.), a principle actor's name, and so on. The EPG data may be communicated to the client 104 in a variety of ways. In one instance, the EPG data 122(m) is broadcast to the client 104 utilizing a carousel file system. The carousel file system repeatedly broadcasts the EPG data over an out-of-band (OOB) channel to the client 104 over the network 106. Although the head end 112 is illustrated as including the EPG data 122(m), in another instance the EPG data 122(m) is provided over the network 106 utilizing a separate EPG data service.

The client 104 may be configured as a computer that is capable of communicating over the network 106, such as a desktop computer, a mobile station, an entertainment appliance, a set-top box 126 that is communicatively coupled to a display device 128 as illustrated, and so forth. Although the set-top box 126 is shown separately from the display device 128, the set-top box 126 may be built into the display device 128 to form an integral unit. The client 104 may also relate to a person and/or entity that operate the client 104. In other words, client 104 may describe a logical client that includes a user and/or a machine. Although one client 104 is illustrated, a plurality of clients may be communicatively coupled to the network 106.

The client 104 may also include a database 130 having locally stored content 132(j), where “j” can be any integer from 1 to “J”. For example, the client 104 may be configured as a DVR that stores the database 130 in hard disk memory. Due to the size of the memory, users are able to record content, such as content 116(n) streamed from the head end 112. As previously described, the DVR also offers control functions, such as the ability to pause content that is currently being broadcast and allows viewers to watch the content while still in progress from the point it was paused. The DVR plays back the content from disk memory, starting at the pause event, while continuing to record the currently-broadcast content in the disk memory. Additionally, the DVR may support other control functions, such as rewinding, fast forwarding a stored program, slow motion playback, and the like.

The client 104 is equipped with sufficient processing and storage capabilities to store and run a navigation module 134. The navigation module 134, when executed on the client 104, provides control functions for interacting with content. For example, the control functions may include the DVR control functions as previously discussed, as well as channel selection, electronic program guide (EPG) navigation, and so on. In another implementation, the navigation module 134 provides media player functionality, such as to play media having audio and/or visual data, such as MP3 data.

In a further implementation, the client 104 may execute the navigation module 134 to cause recordation of the content 116(n) at the distribution server 118. For example, the navigation module 134 may form a request that is communicated to the distribution server 118 over the network 106 to record content 108(k) communicated to the distribution server 130 from the content provider 102. The distribution server 118, in response to the request, records the requested content such that the navigation module 134 operates as a network digital video recorder (NDVR). Thus, through execution of the navigation module 134, the client 104 may playback locally-stored content 132(j), content 116(n) that is stored remotely over the network 106, and may even control the recordation and playback of the remotely stored content 116(n) to the client 104.

Generally, any of the functions described herein can be implemented using software, firmware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations. The terms “module,” “functionality,” and “logic” as used herein generally represent software, firmware, or a combination of software and firmware. In the case of a software implementation, the module, functionality, or logic represents program code that performs specified tasks when executed on a processor (e.g., CPU or CPUs). The program code can be stored in one or more computer readable memory devices. The content recordation techniques described below are platform-independent, meaning that the content recordation techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

The environment 100 supports a variety of techniques for recordation of the content 132(j), 116(n) through use of a recording document 136. The recording document 136, for instance, describes content to be recorded and may conform to an extensible Markup Language (XML) schema that is parsable by a parser module 138 to locate a particular content item. For example, the recording document 136 may describe a title and a start time for a desired content item. The parser module 138 is executed on the distribution server 118 to compare the title and the start time described in the recording document with the EPG data 122(m) stored in the database 120 to determine if and when the particular content item is available. If the particular content item is available, a reference to the particular content item is added to a recording list 140 to cause the particular content item to be recorded. For example, the recording list 140 may be utilized by the distribution server 118 to record content 116(n) at the head end 112 in a NDVR scenario. In another example, the recording list 140 is communicated to the client 104 to cause the navigation module 134 to record content 132(j) locally in a DVR scenario. In a further example, the recording document 136 is communicated from the remote device 142 to the client 104 for parsing by the client 104, an example of which is shown in relation to FIG. 2B.

The recording document 136 may be provided in a variety of ways. As illustrated in FIG. 1, the recording document 136 is stored on a remote device 142 that is communicatively coupled to the network 106. Therefore, a user of the remote device 142 may provide the recording document 136 to the head end 112 to cause recording of content described by the recording document 136. Thus, the recording document 136 may be provided remotely by the remote device 142 such that the user does not need to interact with the client 104 locally to cause recordation of desired content. A variety of other ways of providing the recording document 136 are described in relation to FIGS. 2A, 2B, and 3.

FIG. 2A is an illustration of an exemplary system 200 showing the distribution server 118, the client 104, and the remote device 142 of FIG. 1 in greater detail. The client 104 includes a processor 202 and memory 204. Processors are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions. Alternatively, the mechanisms of or for processors, and thus of or for a computing device, may include, but are not limited to, quantum computing, optical computing, mechanical computing (e.g., using nanotechnology), and so forth. Memory 204 may include one or more memory devices, such as read only memory (ROM), random access memory (RAM), hard disk memory, removable media memory devices, and so on.

The navigation module 134 and the recording list 140 are illustrated as being executed on the processor 202 and are storable in memory 204. The EPG 124 is illustrated as being stored in the memory 204 and is executable on the processor 202. It should be noted that in the illustrated system 200 of FIG. 2A, the recording list 140 is depicted within the client 104 to show that the recording list 140 may be configured for use by the navigation module 134 to cause recordation of content, further discussion of which may be found starting in relation to FIG. 4.

The client 104 may also include a network interface 206 for receiving the content 116(n) of FIG. 1 that is communicated (e.g., streamed) over the network 106. For example, the network interface 206 may be configured as a tuner that receives broadcast content from over the network 106, may be configured as a transmitter/receiver (transceiver) that is suitable for two-way communication over the network 106, and so on. Thus, the network interface 206 may be configured to transmit and receive messages over the network to and from the head end 112 and/or the remote device 142.

Content 116(n) received from the network 106 via the network interface 206 may be stored in the database 130 for later output by the client 104 and/or provide for immediate output of the content 116(n). The database 130 is illustrated as being separate from memory 204, but may also be included in memory 204. For example, the storage device for the database 124 may be configured as a hard disk drive and the memory 204 may be configured as RAM, both the memory 204 and the database 130 may be implemented as RAM, both the memory 204 and the database 130 may be implemented as removable memory, and so forth. The client 104 executes the navigation module 134 to retrieve the content 132(j) from the database 124 and output the content 132(j) through an output interface 208 for rendering on the display device 122. Thus, in this implementation, the client 104 is capable of operating as a DVR that stores and plays back the content 1320(j).

The client 104 may be locally controlled by a user via inputs provided by an input device 210. The inputs are received by the client 104 from an input interface 212 over a local connection 214. The input interface 212, local connection 214 and input device 210 may be configured in a variety of ways. For example, the input interface 212 may be configured as a wireless port, such as an infrared (IR) or Bluetooth wireless port, for receiving wireless communications from input device 210, such as a remote control device, a handheld input device, or any other wireless device, such as a wireless keyboard. In alternate embodiments, the input interface 212 may use an RF communication link or other mode of transmission to communicate with client 104, such as a wired connection which may include a universal serial bus (USB) connection, and so on.

When output of content is requested, the navigation module 134 is executed on the processor 202 to obtain content, such as from content 116(n) of FIG. 1 that is streamed from the distribution server 118 over the network 106, content 132(j) that is stored locally on the database 130, and so on. The navigation module 134 may also restore the content to the original encoded format as provided by the content provider 102 of FIG. 1. For example, content 116(n) of FIG. 1 may be compressed and then streamed from the distribution server 118 to the client 104. Therefore, when the navigation module 134 receives the content, the content may be decompressed for rendering by the display device 128.

The distribution server 118 also includes a processor 216 and memory 218. The parser module 138 is illustrated as being executed on the processor 216 and is storable in memory 218. The memory 218 of the distribution server 118 is also illustrated as including a plurality of client state data 220(l), where “l” can be any integer from 1 to “L”. The client state data 220(l) is utilized to process requests to record content, such as at the head end 112 of FIG. 1 as content 116(n) and/or at the client in database 130 as content 132(j). For example, the distribution server 118 may include a content manager module 222 (hereinafter, “manager module”) that is executable on the processor 216 to manage client 104 content access. The client state data 220(l), for instance, may specify parental blocks to prevent viewing of content items, may specify conditional access rights (e.g., digital access rights) of the client for particular items of content, rating limits, favorite channels, level of service provisioned, and so on. The manager module 222, when executed, may determine if the client 104 is permitted (i.e., authorized) to record the particular content item, and if so, the distribution server 118 causes the client 104, and specifically the navigation module 132, to record the particular content item. In this way, the head end 112 provides an authoritative source for client state data 220(l) in the system 200 and environment 100 as shown, respectively, in FIGS. 1 and 2. In an implementation, the distribution server 118 may be considered the primary source for the client state data 220(l) for a particular client, even over the client 104 itself. For example, by storing the client state data 220(l) on the distribution server 118, a user may switch set-top boxes without transferring client state data between the set-top boxes. Further discussion of use of the client state data 220(l) may be found in relation to FIG. 7.

The remote device 142 is also illustrated as including a processor 224 and memory 226. The recording document 136 is illustrated as being stored in memory 226 and is executable on the processor 224. The remote device 142 also includes a recording module 228 which is illustrated as being executed on the processor 224 and is storable in memory 226. The recording module 228, when executed, generates the recording document 136 for a particular content item. For example, the recording module 228 may provide a user interface for accepting user inputs that describe a particular content item. The user inputs are processed by the recording module 228 to generate a recording document 136 that follows a schema that is understood by the parser module 138. The parser module 138, when executed, parses the recording document 136 to locate and compare descriptive data in the recording document 136 with EPG data 122(m) in the database 120. EPG data 122(m) that matches the descriptive data is then utilized to determine how to record a particular content item described in the recording document 136. A reference to the particular content item is then added to the recording list 140 to cause the navigation module 134 to be executed on the client 104 to record the particular content item. A variety of other scenarios are also contemplated such that the user may cause recordation of content at the client 104 and/or the head end 112 of FIG. 1, further examples of which may be found in relation to the following figure.

FIG. 2B is an illustration of an exemplary system 250 showing the distribution server 118, the client 104, and the remote device 142 of FIG. 1 in greater detail such that the client includes the functionality to parse a recording document. In the system 200 described in relation to FIG. 2A, the distribution server acted as a central repository for client state data 220(L) and executed the parser module 138 to parse the recording document 136.

In the exemplary system 250 illustrated in FIG. 2B, however, the client 104 executes the parser module 138 to parse the recording document 136 that is communicated from the remote device 142 over the network 106. The parser module 138 may then be utilized to populate the recording list 140 as previously described by comparing the recording document 136 with EPG 124 that is stored in the memory 204. Thus, in this instance, the head end 112 acts to broadcast content 116(n) over a broadcast network 252 and does not actively participate in the recordation of the content 132(j) on the client 104, further discussion of which may be found in relation to FIG. 6.

FIG. 3 is an illustration of a system 300 showing a variety of content recordation techniques as implemented by the distribution server 118 and the client 104 of FIG. 2A. One such content recordation technique is the inclusion of the recording document 302 within content 108(k). For example, the client 104 may receive content 108(k) from the content provider 102 of FIG. 1. The content 108(k) in this example is a television program which includes credits which describe the actors, producers, and so on. The credits may also include a preview for next week's episode of the television program. The preview has an embedded recording document 302 which causes an interactive icon to appear that, when selected, allows the user to automatically schedule a recording for the next episode of the television program.

The recording document 302 is then communicated to the distribution server 118 over the network 110 for parsing by the parser module 138. The parser module 138, when executed, locates the particular content item (e.g., the next episode of the television program) based on the recording document 302 and the EPG data 122(m) and adds a reference to the particular content item to a recording list 140. The recording list 140 causes the navigation module 134 to record the content locally in the database 130 as content 132(j). Thus, the recording document 302 embedded in the content 108(k) provides for automatic recording of the next episode of the television program with minimal user intervention.

In another such technique, a remote content recordation technique is provided by using a remote record service 304. For example, the remote record service 304 may provide a web site which enables a user to select content for recording. The web site 304 may then communicate a recording document 306 that describes the content selected by the user to cause the client 104 to automatically record the selected content as previously described.

In a further such technique, the user interacts with the remote device 142 to remotely record content using the client 104. For example, the remote device 142 may execute an email module 308 that causes an email that contains a recording document 310 to be communicated to the distribution server 118. The distribution server 118 may then execute the parser module 138 to compare the descriptive data in the recording document 310 with the EPG data 122(m) to determine if the particular content item referenced in the email is available. If so, the parser module138 may then be executed to determine if access to the particular content item is permitted by the client 104 based on the client state data 220(l). For example, the client state data 220(l) may indicate whether the user subscribes to a content service package that includes the particular content item. If the user does have conditional access rights, the particular content item is added to the recording list 140 for causing the navigation module 134 to record the particular content item as content 132(j) in the database 130.

In another example, the remote device 142 may include a text messaging module 312 to receive a text message from another remote device. The text message may describe a particular content item, such as by providing the title, names of actors, genre, and so on. The text message may be examined to dynamically generate the recording document 310 that contains the content descriptions from the text message. The recording document 310 may then be communicated to the distribution server 118 for processing as previously described. In this example, the recording document 310 is dynamically generated, further discussion of which may be found in relation to FIGS. 5-7. Although the system 300 of FIG. 3 described the execution of the parser module 138 on the distribution server 118, the parser module 138 may also be executed on the client 104. For example, the parser module 138, when executed on the client 104, may compare the descriptive data in the recording document 306 with the EPG 124 (e.g., the EPG data utilized to form the EPG stored on the client 104) to determine availability of the particular content item. Further discussion of execution of the parser module 138 by the client 104 may also be found in relation to FIGS. 5-7. Although a variety of exemplary content recordation techniques have been described, a variety of other content recordation techniques may also be provided that utilize a recording document for comparison with EPG data.

Exemplary Procedures

The following discussion describes content recordation techniques that may be implemented utilizing the previously described systems and devices. Aspects of each of the procedures may be implemented in hardware, firmware, or software, or a combination thereof. The procedures are shown as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks.

FIG. 4 is a flow diagram depicting a procedure 400 in an exemplary implementation in which a recording document is utilized to record a particular content item. At block 402, a recording document 404 is invoked by a remote device 142 for a particular content item. For example, the remote device 142 may access a web site 406 that provides an output of a web page 408 for viewing at the remote device 142. The web page 408, when provided to the remote device 142, may also include the recording document 404 that describes a particular content item. For instance, the web page 408 may include a review of a television show that is available from a broadcast from a head end 112. If the user wishes to record the television show, the user selects a link in the web page 408, which causes the recording document to be invoked.

The recording document 404 in this example follows an XML recording schema. The XML recording schema is an abstract representation depicting the interrelationship between attributes and elements of an XML object, which in this instance is the recording document 404 or a portion of the recording document 404. An example of the recording document 404 which complies with an exemplary XML recording schema is shown as follows: <?xml version=“1.0” encoding=“utf-8” ?> <!-- Sample Click-to-Record (NBC Single-Episode Scenario) --> <clickToRecord xmlns=“urn:schemas-microsoft-com:ehome:clicktorecord”>  <ds:Signature xmlns:ds=“http://www.w3.org/2000/09/xmldsig#”>    <!-- XML Signature goes here -->  </ds:Signature>  <body>    <metadata>      <!-- The following information should be considered insecure unless signed. -->      <description>A very special episode of Friends.</description>      <moreInfoUrl>http://www.nbc.com/friends/</moreInfoUrl>    </metadata>    <!-- hard prepad and postpad 5 minutes - if airing specified isn't found, suggest another one -->    <programRecord prepadding=“5” postpadding=“5” allowAlternateAirings=“true” allowAlternateService=”false”>      <program>       <key field=“urn:schemas-microsoft-com:ehome:epg:program#title” match=“exact”>Friends</key>       <key field=“urn:schemas-microsoft- com:ehome:epg:program#episodetitle” match=“exact”>The One Where Chandler Marries Monica</key>      </program>      <service>       <key field=“urn:schemas-microsoft- com:ehome:epg:service#affiliate” match=“startswith”>NBC</key>      </service>      <!-- Folks in PST have a time (in UTC) specified -->      <airing timeZone=“EST”>       <key field=“urn:schemas-microsoft- com:ehome:epg:airing#starttime”>2003-10-15T08:00:00Z</key>      </airing>      <!-- Other folks record if the show is found within 3 hours of the UTC time specified -->      <airing searchSpan=“180”>       <key field=“urn:schemas-microsoft- com:ehome:epg:airing#starttime”>2003-10-15T08:00:00Z</key>      </siring>    </programRecord>  </body> </clickToRecord> The outermost element <clickToRecord> is the root element of the recording document 404, which is defined by the namespace “urn:schemas-microsoft-com:ehome:clicktorecord”. The <clickToRecord> element contains an element: <body> plus an optional digital signature conforming to an XML Signature specification.

The <body> element contains a single <metadata> element followed by one or more <programRecord> elements. The <metadata> element may encapsulate several sub-elements to providing additional data that describes the requested content item. The following is a list of exemplary <metadata> sub-elements: Element Usage <description> Description of the package (e.g., A Very Special Episode of Friends) <expires> Date/Time after which the recording document expires. <moreInfoUrl> Hyperlink to the source's website (e.g., http://entertainment.msn.com/tv) <updateUrl> Pointer to a URL that may contain updated versions of the recording document to account for schedule changes. One or more record definition elements may be included after the <metadata> element as shown in the above exemplary recording document 404. A <programRecord> record definition element is included which covers both one-time and series recording scenarios.

As shown in the sample document above, the <programRecord> element may include several optional attributes, examples of which are described as follows: De- Attribute fault Usage prepadding/ 0/0 Specifies pre-padding and/or post-padding postpadding of the recording in minutes. For example, padding may be utilized to account for a lack of clock synchronization between the head end 112 of FIG. 1 and the client 104. allowAlternateAirings true Specifies how to handle instances in which a specified broadcast of a content item cannot be found. If this attribute is “true”, a search for the same content item is performed for different scheduled times and the user is informed of the change, if any. If this attribute is“false”, and the show is not found within the specified time window, then the request will fail and the user will be informed. allowAlternateServices false Similar to the “allowAlternateAirings”, however, by specifying “true” different content providers (e.g., broadcasters) may be specified. programDuration 0 Specifies an output duration of the content item. This may be used if the content item is not found in the current EPG and a temporary recording event must be created. If 0, the content item must appear in the guide or the query fails. firstRunOnly false Don't record reruns. daysOfWeek 0x7F Indicates which days of the week a content item may be recorded for manual and generic “keyword” requests. isRecurring false This element differentiates between one- time and series request behavior for the content item.

The <programRecord> element may include a variety of element types as children that further describe the particular content item, such as <program> (e.g., a title of a television program), <service> (e.g., a broadcast channel that provides the television program), and <airing> (e.g., a time when the television program is to be broadcast). Each of these elements may occur more than once in the recording document 404.

At block 410, the remote device communicates the recording document 404 to the head end 112. For example, the recording document 404 may be transmitted (i.e., pushed) over the network 106, implemented using the Internet, for receipt by the head end 112. In another example, the recording document is “pulled” from the remote device 142 by the head end 112. For instance, the head end 112 may be configured to periodically monitor the remote device 142 for presence of the recording document 404.

At block 412, the head end 112 queries the database 120 of EPG data 122(m) to determine if the particular content item described by the recording document 404 is available. The head end 122, for instance, may execute the parser module 138 to locate data in the recording document 404 that describes the particular content item, which is illustrated at block 412 of FIG. 4 as “content description 414”. The content description 414 (i.e., the descriptive data) is then compared with the EPG data 122(m) to find a match. For example, the <program>, <service>, and <airing> elements may be compared with the EPG data 122(m) to find a particular content item which most satisfies those elements. Thus, the parser module 138, when executed, may determine how to record the particular content item that is described by the recording document by cross-referencing the content description 414 with the EPG data 122(m).

In an implementation, the head end 112 utilizes minimum search field requirements before querying the database that contains EPG data 122(m) (block 412). For example, specific combinations of search criteria, when included in a recording document, may result in a failure in the query (block 412) due to insufficient amount of information (e.g., elements) to locate the particular content item. For instance, a recording document that only specifies a <service> (e.g., a broadcast channel) may be considered as invalid unless a corresponding <program> and/or <airing> is provided. The following is a listing of exemplary legal combinations of the three elements previously described:

<program> (e.g., record this program anytime it is streamed, on any service);

<program>, <service> (record this program anytime it is streamed from a specified service);

<program>, <airing> (record this program at this time from any service);

<program>, <service>, <airing> (record this program at this time from this service); and

<service>, <airing> (record the named service at the given time). Although three elements are described, a variety of other elements and combinations thereof may also be included in the recording document 404 to locate a particular content item.

Through use of elements and different combinations of the elements, for example, search criteria may be broadly or narrowly specified depending upon the desired implementation. For instance, a fan website may post a recording document for recording any episode of a particular television program no matter what time it is broadcast and no matter which channel broadcasts the television program. Such a recording document may specify the title of the television program (e.g., <program>) without supplying any other additional elements. In another instance, a website provided by a particular content broadcaster may supply a recording document that specifies episodes that are broadcast by that particular content broadcaster and does not wish to include episodes that are broadcast by rival broadcasters. In this instance, the recording document specifies the title of the television program (e.g., <program>) and the broadcaster (e.g., <service>).

Although some examples of search criteria have been described, a variety of other search criteria may also be specified in a recording document. For example, the recording document may specify alternative matching attributes, such as “(<program> and <service>) or (<service> and <airing>)”. Additionally, each of the elements may be specified in a variety of ways. For instance, a target service may be specified by call sign, name, affiliate, and so on. Thus, the recording document may flexibly describe search criteria as contemplated by a creator of the recording document.

The search criteria (i.e., elements) may also be processed so that the recording document is transportable between users having different respective content providers. For example, users may receive content through different channel lineups, the users may be located in different time zones, and so on. Time-based search criteria, for instance, may be specified using any time-zone and then normalized to a local time-zone when parsed. In another instance, the search criteria may be restricted to within a particular offset from coordinated universal time (UTC). Multiple criteria may be specified in this way so one time can be specified that applies only to Pacific Standard Time (PST) and Eastern Standard Time (EST), for example, and another time set for Mountain Standard Time (MST) and Central Standard Time (CST). In a further instance, a search “window” can be specified to allow the episode to be matched within a specific range of time around the time specified.

If the particular content item is available, then the head end adds a content reference 418 to the particular content item in the recording list 140 (block 416). The content reference 418, for instance, may specify a broadcast channel and time to record the referenced content item, map to a memory location of the particular content item in a database 114 of FIG. 1 at the head end 112, and so on.

At block 420, the head end 112 causes the client 104 to record the particular content item referenced in the recording list 140. For example, the head end 112 may execute the parser module 138 to communicate the content reference 418 over the network 106 to the client 104. The navigation module 134, upon receipt of the content reference 418, records the particular content item to the database 130 as specified by the content reference 418. Thus, in this example, the remote device 142 is able to cause the client 104 to record a particular content item without direct interaction with the client 104.

FIG. 5 is an illustration of a system 500 in an exemplary implementation in which a graphical user interface (GUI) 502 is provided by the recording module 228 to dynamically generate the recording document 136 based on user input. In the previously described procedure 400 of FIG. 4, the recording document 404 was preconfigured and obtained to record a particular content item. The recording document may also be dynamically generated based on user input to describe a particular content item for recording.

The remote device 142, for example, includes the recording module 228. The recording module 228, when executed on the remote device 142, provides an output for display on a display device 504 of the GUI 502. The GUI 504 in this example provides an interface for entering keyword search elements which may be utilized to locate a particular content item. For instance, the user may utilize an input device to enter a portion of a title and actors in the particular content item, such as “Godfather” 506, “Pacino” 508, and “DeNiro” 510. The recording module 228 utilizes these elements to form the recording document 136. The recording document 136 is then communicated over the network 106 to the distribution server 118 and parsed by the parser module 138 as previously described to determine if the described particular content item of the recording document 136 is available.

In this example, the elements “Godfather” 506, “Pacino” 508 and “De Niro” 510 are utilized to determine if the particular content item “Godfather II” is available by finding a content item described in the EPG data 122(m) of FIG. 1 that satisfies each of these elements. In another implementation, a “best match” may be performed so that the content item described in the EPG data 122(m) which satisfies the most elements in the recording document 136 is reported to the user via the GUI 504. For example, Godfather II may not be available based on a query of the EPG data 122(m). However, the movie Godfather I, which satisfies the elements “Godfather” 506 and “Pacino” 508 may be available. Therefore a result of the query, which indicates the availability of Godfather I, is output via the GUI 504 so that the user can decide whether to record that particular content item.

FIG. 6 is an illustration of a system 600 in an exemplary implementation in which the recording module is executed to examine a textual description of content to dynamically generate a recording document. In the system 500 of FIG. 5, the recording document 136 was dynamically generated based on user input. The recording document 136 may also be dynamically generated without user input.

The client 104, for instance, may be configured as a set-top box 126 that is communicatively coupled to the display device 128. The client 104 executes the navigation module 134 to access a textual description of a particular content item over the network 106, which in FIG. 6 is illustrated as a content review 602 that is available from a web site. The user, upon reading the content review 602, may desire to record the particular content item described in the review. In this instance, however, the content review 602 does not include a preconfigured recording document as previously described in relation to FIG. 3. Therefore, the client 104 executes a recording module 604 to dynamically generate the recording document 136 based on the content review 602.

The recording module 604, for example, may be executed to examine the content review 602 to find one or more words which describe the particular content item. In an implementation, the recording module 604 compares words in the content review 602 with a database 606 of descriptive words which may be utilized to describe content, such as names of broadcast channels, titles, actors, and so on. For instance, the recording module 604, when executed, locates the words “hardball” 608, “Chris Matthews” 610, and “MSNBC” 612 (MSNBC is a trademark of MSNBC Cable L.L.C. of New York, N.Y.). The recording module 604 then generates a recording document 614 and communicates it over the network 106 to a parser module 616 that is executable on another client 618.

The parser module 616, when executed on the other client 618, compares the recording document 614 with an EPG 620 to determine if the particular content item described in the recording document 614 is available, and if so, causes a navigation module 622 to record the particular content item as content 624(p), where “p” can be any integer from one to “P”, in the database 626.

In another implementation, the recording module 604 and the parser module 616 are executed to directly compare words 608-612 in the content review 602 with the EPG 124 that is stored on the client 104. In other words, the EPG 124 (and more particularly the EPG data that is utilized to configure the EPG 124) provides the database 606. In this implementation, the recording module 604 does not wait until after the recording document 608 is completely generated to perform the comparison, but rather compares words 608-612 with the EPG 124.

It should be noted that in the system 600 of FIG. 6, the client 104 executes the recording module 604 to generate the recording document 136. Another client 618 executes the parser module 616 to determine if the particular content item is available based on another EPG 620 that is stored locally on the other client 618. Thus, the content recordation techniques may also be utilized for interaction between clients 104, 618 without directly involving the head end 112 of FIG. 1. Further discussion of client execution of the parser module may be found in relation to the following figure.

FIG. 7 is a flow diagram depicting a procedure 700 in an exemplary implementation in which a client dynamically generates a recording document that is utilized to determine availability of a particular content item for recording by the client. At block 702, the client displays a textual description of a particular content item. A variety of textual descriptions may be displayed, such as the content review 602 of FIG. 6, an email, a text message communicated from another client, and so on.

At block 704, the client receives an input to active a recording module. For example, the client may provide an icon for selection by the user, a drop-down menu for activation of the recording module, and so on. At block 706, the recording module, when executed, examines the text to locate descriptions of the particular content item. For instance, the recording module may first examine the text to locate words which are typically used to describe the <program>, <service>, and <airing> elements that were previously described. The recording module may also locate other words which describe the particular content item, such as actor, output duration of the content, genre, start time, stop time, plot, and so on.

At block 708, the recording module generates a recording document that includes the located descriptions of the particular content item. The recording document, for instance, may be configured according to an XML recording schema that is understood by the parser module. The recording module then passes the recording document to the parser module (block 710).

At block 712, the parser module queries EPG data to locate the particular content item. In a first scenario, the parser module is executed on the client to query an EPG that is stored locally on the client. In a second scenario, the parser module is executed on the client to query EPG data that is stored at the head end, such as the EPG data 122(m) stored in the database 120 at the head end 112 of FIG. 1.

At decision block 714, a determination is made as to whether the located content item conflicts with another content item in the recording list. For example, the recording list may be configured for implementation by a DVR that is capable of recording a single content item at any one point in time. Therefore, the parser module may be executed to flag conflicts in the recording list so that the referenced content items are recorded as desired. If there is a conflict (block 714), a message is sent to the user (block 716) so that the user may decide which of the conflicting content items is to be recorded, if any.

If the located content item does not conflict with another content item in the recording list (block 714), a determination is made as to whether the client is authorized to record the content (block 718). For example, the parser module may be executed to determine from the client state data 220(l) stored at the distribution server 118 of FIG. 2 whether the client is permitted to access the referenced content item. The client state data 220(l), for instance, may be utilized to indicate a variety of conditional access rights, such as parental blocks, digital rights management (DRM), content subscriptions, and so on.

If the client is authorized to record the content (block 718), then the located content item is added to a recording list (block 720). For instance, a reference to the located content item may be added which describes how to record the located content item, such as date, time, and channel of a broadcast of a television program, a memory location, and so on. The recording list may then be utilized to cause the navigation module to record the added content item (block 722).

CONCLUSION

Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed invention. 

1. A method comprising: querying electronic program guide (EPG) data to determine if a content item described in a recording document is available for recording; and if the content item is available, adding a reference in a recording list for causing recordation of the content item.
 2. A method as described in claim 1, wherein the querying is performed by execution of a parser module on a head end.
 3. A method as described in claim 1, wherein: the querying is performed by execution of a parser module on a head end; and the reference in the recording list is for causing recordation of the content item by a client.
 4. A method as described in claim 1, wherein the querying is performed by execution of a parser module on a client.
 5. A method as described in claim 1, wherein: the query is performed at a client; and the reference in the recording list is for causing recordation of the content item at a head end.
 6. A method as described in claim 1, further comprising determining if the available content item conflicts with another content item in the recording list.
 7. A method as described in claim 1, further comprising examining client state data that describes conditional access rights of a plurality of clients to determine if recordation of the content item for a particular said client is permitted.
 8. A method as described in claim 1, wherein the recording document describes the content item through at least one of a restrictive criterion, a service, a time, or a genre.
 9. A method as described in claim 1, further comprising generating the recording document from a textual description of the content item.
 10. A method as described in claim 9, wherein the textual description is selected from the group consisting of: one or more words entered by a user via a user interface; an article; a text message; an email; and another content item.
 11. One or more computer readable media comprising computer executable instructions that, when executed by a computer, direct the computer to perform the method as described in claim
 1. 12. A method comprising: examining a textual description to locate one or more words that describe a content item; comparing the one or more words with electronic program guide (EPG) data to determine if the content item is available for recording; and if the content item is available, adding a reference in a recording list to cause recordation of the content item.
 13. A method as described in claim 12, wherein the textual description is selected from the group consisting of: one or more words entered by a user via a user interface; an article; a text message; an email; and another content item.
 14. A method as described in claim 12, wherein the content item is selected from the group consisting of: a television program; a movie; a picture; a music file; and media.
 15. A method as described in claim 12, wherein: the examining is performed by executing a recording module on a client; and the comparing and the adding are performed by executing a parser module on a head end.
 16. A method as described in claim 12, wherein the examining, the comparing, and the adding are performed by executing a recording module and a parser module on a client.
 17. A method as described in claim 12, further comprising generating a recording document that includes the located one or more words.
 18. A method as described in claim 12, further comprising: generating a recording document that includes the located one or more words; communicating the recording document to a head end which executes a parser module to perform the comparing and the adding; and communicating the recording list to a client to cause recordation of the content item described in the EPG data through execution of a navigation module on the client.
 19. A method as described in claim 12, further comprising determining if the client is authorized to record the content item.
 20. A method as described in claim 19, wherein the determining is performed at a head end using client state data that is stored on the head end.
 21. One or more computer readable media comprising computer executable instructions that, when executed by a computer, direct the computer to perform the method as described in claim
 12. 22. One or more computer readable media comprising computer executable instructions that, when executed by a computer, direct the computer to: examine a textual description to locate one or more words that describe a content item; generate a recording document having the one or more words; and form a communication for communicating the recording document for comparison with electronic program guide (EPG) data to determine if the content item described by the recording document is available for recording.
 23. One or more computer readable media as described in claim 22, wherein the computer executable instructions further direct the computer to: determine if the content item described by the recording document is available for recording; and if the content item is available, add a reference to the available content item to a recording list.
 24. One or more computer readable media as described in claim 22, wherein the computer executable instructions further direct the computer to examine client state data that describes conditional access rights of a plurality of clients to determine if recordation of the content item for a particular said client is permitted.
 25. One or more computer readable media as described in claim 22, wherein the computer executable instructions further direct the computer to determine if the available content item conflicts with another content item in a recording list.
 26. One or more computer readable media as described in claim 22, wherein the textual description is selected from the group consisting of: one or more words entered by a user via a user interface; an article; a text message; an email; and another content item.
 27. A head end comprising: a processor; and memory configured to maintain: electronic program guide (EPG) data; a recording document having a plurality of elements which describe a content item; and a parser module that is executable on the processor to: determine if the content item described in the recording document is available for recording by comparing at least one said element with the electronic program guide (EPG) data; and if the content item is available, add a reference to a recording list for causing recordation of the content item.
 28. A head end as described in claim 27, wherein the reference in the recording list is for causing recordation of the content item in the memory.
 29. A head end as described in claim 27, wherein the reference in the recording list is for causing recordation of the content item at a client.
 30. A head end as described in claim 27, wherein the parser module is further executable on the processor to generate the recording document from a textual description of the content item.
 31. A head end as described in claim 30, wherein the textual description is selected from the group consisting of: one or more words entered by a user via a user interface; an article; a text message; an email; and another content item.
 32. A head end as described in claim 27, wherein the parser module is further executable on the processor to examine client state data that describes conditional access rights of a plurality of clients to determine if recordation of the content item for a particular said client is permitted.
 33. A head end as described in claim 27, wherein the parser module is further executable on the processor to determine if the available content item conflicts with another content item referenced in the recording list.
 34. A client comprising: a processor; and memory configured to maintain: an electronic program guide (EPG) formed from a plurality of EPG data; a recording document having a plurality of elements which describe a content item; and a parser module that is executable on the processor to: determine if the content item described in the recording document is available for recording by comparing at least one said element with the electronic program guide (EPG) data; and if the content item is available, add a reference in a recording list, based on the query, for causing recordation of the content item.
 35. A client as described in claim 34, wherein the reference in the recording list is for causing recordation of the content item at a head end.
 36. A client as described in claim 34, wherein the reference in the recording list is for causing recordation of the content item through execution of a navigation module on the client.
 37. A client as described in claim 34, wherein the parser module is further executable on the processor to generate the recording document from a textual description of the content item.
 38. A head end as described in claim 37, wherein the textual description is selected from the group consisting of: one or more words entered by a user via a user interface; an article; a text message; an email; and another content item.
 39. A client as described in claim 34, wherein the parser module is further executable on the processor to examine client state data, which describes conditional access rights, to determine if recordation of the content item is permitted.
 40. A client as described in claim 34, wherein the parser module is further executable on the processor to determine if the available content item conflicts with another content item in the recording list.
 41. A system comprising: a network; a head end that is communicatively coupled to the network, includes a database having electronic program guide (EPG) data, and has a parser module that is executable thereon to: query the EPG data to determine if a content item described in a recording document received from over the network is available for recording; if the content item is available, examine client state data that describes conditional access rights of a plurality of clients to determine if recordation of the content item for a particular said client is permitted; if recordation of the content item for the particular said client is permitted, add a reference in a recording list for causing recordation of the content item; and form a communication for communicating the recording list via the network; and the particular said client that is communicatively coupled to the network and includes a navigation module that is executable thereon to: receive the communication having the recording list; and record the referenced content item. 